This repository was archived by the owner on Aug 2, 2020. It is now read-only.
Update @neogeek/eslint-config-standards to the latest version 🚀 #15
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Version 3.0.0 just got published.Update to this version instead 🚀 Release Notesv3.0.0
CommitsThe new version differs by 11 commits.
See the full diff |
Version 4.0.0 just got published.Update to this version instead 🚀 Release Notesv4.0.0
CommitsThe new version differs by 9 commits.
See the full diff |
Version 4.1.0 just got published.Update to this version instead 🚀 Release Notesv4.1.0
|
Update to this version instead 🚀 Release Notes for v4.2.0
CommitsThe new version differs by 11 commits.
See the full diff |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 2.0.0 of @neogeek/eslint-config-standards just got published.
The version 2.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of @neogeek/eslint-config-standards.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v2.0.0.eslint-reactconfig file.Commits
The new version differs by 15 commits.
4be8102Version bump.a9a2a0aSet package to use caret range.71fb1d4Switched from cheerio to JSDOM.2a9155eWhitespace.b90d290Added package-lock.json file to gitignore config.cc077eeUpdated rules.29e98afUpdated eslint.3a9ab4fRemoved Makefile from .npmignore46acf31Added .eslint-react config.4ad4b97Converted from Makefile to npm scripts.c5b8ba5Removed eslint:recommended from main .eslintrc file.2b51250Updated package.6d2bc00Merge pull request #22 from neogeek/greenkeeper/eslint-3.19.0c78cf6achore(package): update eslint to version 3.19.073dcb8fUpdated devDependencies to use caret ranges.See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴